|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
All are approved IETF documents
|
|
3.
|
Justification for the specific reference:
|
|
|
Appendix Provides a mapping between terms in Y.1540 and RFC 5136.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=5136
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC was approved in Feb 2008..
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Informational IETF Stream document Feb 2008
.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
7.1. Normative References/
/
/
[RFC1812] Baker, F., "Requirements for IP Version 4 Routers",/
RFC 1812, June 1995./
/
[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,/
"Framework for IP Performance Metrics", RFC 2330,/
May 1998./
/
7.2. Informative References/
/
/
[PDM] Dovrolis, C., Ramanathan, P., and D. Moore, "Packet/
Dispersion Techniques and a Capacity Estimation/
Methodology", IEEE/ACM Transactions on Networking 12(6):/
963-977, December 2004./
/
[RFC3095] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H.,/
Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le,/
K., Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K.,/
Wiebke, T., Yoshimura, T., and H. Zheng, "RObust Header/
Compression (ROHC): Framework and four profiles: RTP, UDP,/
ESP, and uncompressed", RFC 3095, July 2001./
/
[RFC3148] Mathis, M. and M. Allman, "A Framework for Defining/
Empirical Bulk Transfer Capacity Metrics", RFC 3148,/
July 2001./
/
[V44] ITU Telecommunication Standardization Sector (ITU-T)/
Recommendation V.44, "Data Compression Procedures",/
November 2000./
/
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
